Systems and methods for generating insurance business plans

ABSTRACT

Techniques described herein relate to computer-implemented systems and methods for generating an insurance business plan. The method includes receiving an identification of an agent associated with the insurance business plan and a selection of a future time period for the insurance business plan. A business plan objective graphical user interface (GUI) is displayed, presenting for selection a plurality of insurance business plan objectives, wherein one of the objectives is to grow or maintain insurance policy counts for one or more insurance lines of business. The business plan objective GUI receives a selection of the objective to grow or maintain insurance policy counts for one or more lines of business. Based on a determination that the objective to grow or maintain insurance policy counts for one or more lines of business has been selected, a plurality of insurance lines of business is displayed. The business plan objective GUI receives a selection of an insurance line of business of the plurality of insurance lines of business. Insurance policy information for insurance policies assigned to the agent in the selected line of business is retrieved from an insurance policy database over a network. Additionally, displayed is a goal setting GUI for the selected line of business, the goal setting GUI being populated based on the retrieved insurance policy information and including a policy count chart showing a number of insurance policies assigned to the agent having a selected status, among a plurality of statuses, during a historical period of time through the present and showing a number of polices projected to have the selected status during the selected future time period of the business plan.

TECHNICAL FIELD

This disclosure relates to insurance and, more particularly, tocomputer-implemented systems and methods using graphical user interfacesfor insurance business planning.

BACKGROUND

Typical office management software and/or platforms provide generalbusiness planning and compensation management capabilities, but fail toprovide cross-platform, and cross business, solutions. Consequently,such office management software and/or platforms typically constitutewaste in the form of end user manual work and or use, training, and/ordependency on multiple, disparate management software and/or platformswhich leads to numerous inefficiencies. For example, end users generallyrequire and rely on various manual processes and paperwork to managetheir business and office staff. Conventional management softwareproducts generally fail provide comprehensive and business-need specificsolutions that help end users (e.g., office personnel, agent(s), etc.)manage their office and business effectively. For example, such officesoftware management products are generally narrowly focused, and havelimited capabilities, and, thus, require an office to utilize multiplesoftware products which can lead to inefficiencies, includingredundancies and desynchronized data. In addition, data failures andredundancy in such office management products leads to potential errorsand/or poor insights into real-time statuses of a plurality of businessissues. For example, end users may be forced to manuallysynthesize/derive the information from paper files or non-integratedoffice management software products to perform evaluations or analysis,e.g., such as evaluating a team member's performance.

The disjoint and non-synchronous information of conventional officemanagement software platforms creates several problems. For example, inthe context of insurance, it makes business planning a tedious,fill-in-the-blank process using templates that require an agent to know,or find, all the relevant information needed for an effective plan, andthen to choose goals for various lines of business without a goodknowledge of the historical trends in his/her agency's performance. Theresulting plans are not shared with any other tools or data sources andoften come to a dead end for agents. Planning is something most agentsdo once a year to qualify for various incentive programs and then thenput aside until it is time to plan for the next year. Thus, the businessplans generated in this fashion provide little or no actual value toagents during the year as they manage their business.

For the foregoing reasons, there is a need for improved applications forinsurance business planning.

SUMMARY

To address these and other problems and inefficiencies, this disclosuredescribes methods and systems for generating an insurance business plan.One aspect of the disclosure relates to a computer-implemented methodfor generating an insurance business plan. The method may includereceiving an identification of an agent associated with the insurancebusiness plan and a selection of a future time period for the insurancebusiness plan. The method may include displaying a business planobjective graphical user interface (GUI) presenting for selection aplurality of insurance business plan objectives, wherein one of theobjectives is to grow or maintain insurance policy counts for one ormore insurance lines of business. The method may include receiving, viathe business plan objective GUI, a selection of the objective to grow ormaintain insurance policy counts for one or more lines of business anddisplaying for selection, based on a determination that the objective togrow or maintain insurance policy counts for one or more lines ofbusiness has been selected, a plurality of insurance lines of business.Additionally, the method may include receiving, via the business planobjective GUI, a selection of an insurance line of business of theplurality of insurance lines of business and retrieving, from aninsurance policy database over a network, insurance policy informationfor insurance policies assigned to the agent in the selected line ofbusiness. Finally the method may include displaying a goal setting GUIfor the selected line of business, the goal setting GUI being populatedbased on the retrieved insurance policy information and including apolicy count chart showing a number of insurance policies assigned tothe agent having a selected status, among a plurality of statuses,during a historical period of time through the present and showing anumber of polices projected to have the selected status during theselected future time period of the business plan.

Another aspect relates to a computer-readable storage medium storinginstructions that, when executed by a processor, cause the processor toperform a method for generating an insurance business plan. The methodmay include receiving an identification of an agent associated with theinsurance business plan and a selection of a future time period for theinsurance business plan. The method may include displaying a businessplan objective graphical user interface (GUI) presenting for selection aplurality of insurance business plan objectives, wherein one of theobjectives is to grow or maintain insurance policy counts for one ormore insurance lines of business. The method may include receiving, viathe business plan objective GUI, a selection of the objective to grow ormaintain insurance policy counts for one or more lines of business anddisplaying for selection, based on a determination that the objective togrow or maintain insurance policy counts for one or more lines ofbusiness has been selected, a plurality of insurance lines of business.Additionally, the method may include receiving, via the business planobjective GUI, a selection of an insurance line of business of theplurality of insurance lines of business and retrieving, from aninsurance policy database over a network, insurance policy informationfor insurance policies assigned to the agent in the selected line ofbusiness. Finally the method may include displaying a goal setting GUIfor the selected line of business, the goal setting GUI being populatedbased on the retrieved insurance policy information and including apolicy count chart showing a number of insurance policies assigned tothe agent having a selected status, among a plurality of statuses,during a historical period of time through the present and showing anumber of polices projected to have the selected status during theselected future time period of the business plan.

And yet another aspect relates to a computer terminal having a memorystoring computer program instructions and one or more processorsconfigured to execute the instructions to perform a method forgenerating an insurance business plan, including to receive input of anidentification of an agent associated with the insurance business planand a selection of a future time period for the insurance business plan.The one or more processors may further execute the instruction todisplay a business plan objective graphical user interface (GUI)presenting for selection a plurality of insurance business planobjectives, wherein one of the objectives is to grow or maintaininsurance policy counts for one or more insurance lines of business. Theone or more processors may further execute the instruction to receive,via the business plan objective GUI, a selection of the objective togrow or maintain insurance policy counts for one or more lines ofbusiness and to display for selection, based on a determination that theobjective to grow or maintain insurance policy counts for one or morelines of business has been selected, a plurality of insurance lines ofbusiness. The one or more processors may further execute the instructionto receive, via the business plan objective GUI, a selection of aninsurance line of business of the plurality of insurance lines ofbusiness and to cause the retrieval, from an insurance policy databaseover a network, insurance policy information for insurance policiesassigned to the agent in the selected line of business. Finally, the oneor more processors may further execute the instruction to display a goalsetting GUI for the selected line of business, the goal setting GUIbeing populated based on the retrieved insurance policy information andincluding a policy count table showing a number of insurance policiesassigned to the agent having each of a plurality of statuses during thehistorical period of time through the present and projected to have eachof the plurality of statuses during the selected future period of timeof the business plan.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an example of an insurance providersystem including an insurance business planning system, consistent withthe disclosed embodiments;

FIG. 2 shows a representation of software tools associated with theinsurance business planning system of FIG. 1 , consistent with thedisclosed embodiments;

FIG. 3 shows a representation of a business planning software tool 202among the software tools of FIG. 2 , consistent with the disclosedembodiments;

FIG. 4 shows a representation of an exemplary plan selection graphicaluser interface (GUI) of the business planning software tool of FIG. 3 ;

FIG. 5 shows a representation of an exemplary business plan objectiveGUI of the business planning software tool, consistent with thedisclosed embodiments;

FIG. 6 shows an example of the business plan objective GUI afterselection of a grow or maintain my policy count interface element,consistent with the disclosed embodiments;

FIG. 7 shows an example of the business plan objective GUI afterselection of a compensation interface element, consistent with thedisclosed embodiments;

FIG. 8 shows an example of the business plan objective GUI afterselection of an incentive program interface element, consistent with thedisclosed embodiments;

FIG. 9 shows an example of the business plan objective GUI afterselection of a small business premier program interface element,consistent with the disclosed embodiments;

FIGS. 10, 12, and 13 show examples of auto insurance, fire insurance,and life insurance goal setting GUIs, respectively, consistent with thedisclosed embodiments;

FIG. 11 shows the auto insurance goal setting GUI of FIG. 10 uponselection of a current year view, consistent with the disclosedembodiments;

FIG. 14 shows a representation of a computing device used by agents ofan insurance provider to access the access insurance business planningsystem of FIG. 1 ; and

FIG. 15 shows an exemplary method of creating an insurance businessplan, consistent with the disclosed embodiments.

DETAILED DESCRIPTION

Reference will now be made in detail to specific embodiments orfeatures, examples of which are illustrated in the accompanyingdrawings. Wherever possible, corresponding or similar reference numberswill be used throughout the drawings to refer to the same orcorresponding parts.

FIG. 1 illustrates an example of an insurance provider system 100,consistent with the disclosed embodiments. Insurance provider system 100may include a plurality of insurance policy databases 102 incommunication, over an electronic communication network 104, with aninsurance business planning system 106 operated by insurance agents 108team members working on behalf of the insurance provider operatinginsurance provider system 100. Hereinafter, agents 108 and/or the teammembers may alternatively be referred to a “users” of insurance businessplanning system 106.

Insurance policy databases 102 may store information about insurancepolicies held by customer policy holders of insurance provider system100 and managed by and/or assigned to agents 108. For example, autoinsurance policy database 110, fire insurance policy database 112, andlife insurance policy database 114 may respectively store informationfor automobile, fire, and life insurance policies held by the customersof insurance provider system 100. Although not shown, depending upon theparticular implementation or insurance provider, insurance providersystem 100 may include additional insurance policy databases 102, suchas renter's, liability, motorcycle, motor home, flood insurance., etc.databases.

In some cases, insurance policy databases 102 may be associated withcomputing systems of different insurance companies that underwrite orservice insurance policies on behalf of the insurance provider operatinginsurance provider system 100. Thus, insurance policy databases 102 may,for example, be part of legacy systems, platforms, or services usingdisparate data communication protocols and/or data formats. As discussedbelow, in such cases, insurance business planning system 106 may beconfigured to collate and integrate the disparate information frominsurance policy databases 102 in order to carry out the processesdiscussed herein, including generating insurance business plans foragents 108. In contrast to preexisting systems, insurance providersystem 100 may reduce the time for agents 108 to search for and acquirethe information needed to make a business plan. This allows them tofocus on the task at hand rather than the logistics of gathering andcollating the necessary insurance information, allowing agents 108 tocreate a better plan and make data-driven decisions with less guesswork.

Insurance business planning system 106 may be a computing system, suchas a server system, associated with the insurance provider. As shown inFIG. 1 , insurance business planning system 106 may have a dataintegration component 115 configured to receive insurance policyinformation from insurance policy databases 102 over network 104. Dataintegration component 115 may be configured to collate and integrate thedisparate information received from insurance policy databases 102 intoa consistent format for use by insurance business planning system 106.For example, data integration component 115 may receive the insurancepolicy information from each insurance provider database 102 containedin differing types of markup languages files—such as JavaScript objectnotation (JSON) files, flexible data structures, or other types ofmetadata files—and may convert the differing file types into the samefile format such as XML.

Also as shown in FIG. 1 , insurance business planning system 106 mayinclude a business plan database 116 storing business plans for agents108 generated by insurance business planning system 106, as discussedbelow. It is noted that business plan database 116 and insurance policydatabases 102 may comprise any type of database known in the art. Thisincludes, for example, relational databases such as IBM's DB2,PostgreSQL, or ORACLE databases. Alternatively, databases 102, 116 maycomprise unstructured databases storing information in a markup languagesuch as XML or JSON that may be used with flexible client-server orinterface libraries such as React, jQuery, or other similar interfacesto access the data stored in databases 102, 116.

As shown in FIG. 1 , insurance business planning system 106 may beconfigured to provide an agency suite of software tools 118 for use byagents 108. Software tools 118 may include business management tools,applications, and/or analytical capabilities to assist users in creatingagency business goals and aligning those goals with the enterprise goalsof the insurance provider and thereby grow agency-related businessappropriately and efficiently.

FIG. 2 shows a representation of software tools 118 consistent with thedisclosed embodiments. In one embodiment, software tools 118 may beindependent but unified and/or cross-platform tools or components usingassociated graphical user interfaces (GUIs) to carry out variousbusiness-related tasks. For example, software tools 118 may include abusiness planning software tool 202, a digital whiteboard software tool204, a team member incentives software tool 206, and a reportingsoftware tools 208. In some embodiments, software tools 202-208 maycommunicate, or interoperate with one another within insurance providersystem 100.

Business planning software tool 202 may include, for example, integratedGUIs that assist users such as agents 108 to create agency businessgoals; align enterprise, territory, and agency goals; identify necessaryactions to achieve those goals; and establish a baseline to accuratelymonitor and track progress. Business planning software tool 202 isdiscussed in detail below with respect to FIGS. 3-15 .

Digital whiteboard software tool 204 may include, for example,integrated GUIs with a customizable electronic whiteboard to track salesand service activities. For example, in some embodiments, digitalwhiteboard reports may be generated based on activity type or othermetrics as described herein. In various embodiments, digital whiteboardentry data may receive data from or send data to other elements ofinsurance provider system 100, such as insurance policy databases 102and/or 112. In some embodiments, digital whiteboards may bepre-populated with data, eliminating the need for manual entries intothe digital whiteboard.

Digital whiteboards generated with digital whiteboard software tool 204may provide agents 108 with a customizable electronic whiteboard fortracking production and service activities. Through insurance businessplanning system 106, the digital whiteboard may offer permanent datacapture solutions across various activities. For example, a digitalwhiteboard may be used to electronically assign activities to agentsand/or other team members. In some embodiments, entering of quotes,applications, and other activities may be automated by the digitalwhiteboard. In addition, digital whiteboards may include a reportingcapability that allows agents to access detailed activity reports byteam member or level at an office level. In some embodiments, digitalwhiteboards may provide agents 108 or team members with the abilityachieve business goals by being able to set clear expectations, monitorand lead team sales and service activities in real-time and identifycoaching opportunities for team members.

Team member incentives software tool 206 may include integrated GUIsthat enable agents or other team members to set-up compensation andincentive plans for each of their team members based on production andactivity data. Such embodiments may utilize data and entries from thedigital whiteboards discussed above.

Reporting software tool 208 may include, for example, integrated GUIsthat provide users with views or renderings of integrated actualproduction and activity reports. For example, in some embodiments,reporting software tool 208 may pull data from automatic weeklyproduction reports. Such an implementation may integrate an automaticcomparison of business plan goals with actual production that can beviewed as a dashboard on integrated GUI(s).

FIG. 3 shows a representation of business planning software tool 202 inmore detail. Business planning software tool 202 may be an interactiveapplication allowing agents 108, or other team members, to create and/orupdate an electronic business plan, among other things. For example,using a goals component 300, agents 108 may choose to electronically setand distribute business plan goals and action plan items to individualteam members. In such embodiments, an electronic business plan mayautomatically be saved and may be easily be accessed over a period oftime (e.g., a year). Additionally, or alternatively, the electronicbusiness plan may allow for mobile access via smart phone or tabletthrough components as described herein and/or mobile platforms orapplications (apps).

In a further example, a strategy component 302, which may includebusiness specific tools (e.g., an Auto Gain Strategy tool and/or a FireGain Strategy tool), may be built-in and part of the goal-based feature.The tools may include components that determine what specific activitiesare needed to accomplish the set goals.

In a further example, an action plan component 304 may be used with thegoal and strategy components 300, 302 and allow the agent 108 or otherteam member to identify what specific marketing activities are needed toaccomplish the desired goal. This allows the user to start thinkingabout how the goals will be accomplished.

In a further example, a goal distribution component 306 may be used toidentify team members who will be responsible for what activities andgenerate a team plan. The goal distribution component 306 may be used todistribute goals and action items. In some embodiments, team members maybe assigned their own, smaller team member plan as part of a lagerelectronic plan. Such detailed level of planning may result in sharedaccountability among the team. Various integration GUIs, as describedherein, may provide access to the goal-distribution based feature, e.g.,to visit their distributed/assigned goal.

In a further example, a team access component 308 may be used to allowteam members, regardless of status, to access insurance provider system100. Agents 108 or other team members may allow a business plan, orcertain parts thereof, to become a shared team goal.

In a further example, a reporting component 310 may include integrated,automatic reporting and dashboards on an application layer (e.g., ahomepage) for weekly updates with the most recent data available foreach line of insurance business. In some embodiments, business planningsoftware tool 202 may implement the reporting feature.

In a further example, a target component 312 may be used determine orgenerate reports showing goals and actual production and generatedashboards that compare set goals to actual production. Such reportsand/or dashboards may help end user(s) monitor progress throughout ayear, weekly basis, or other time period.

In various embodiments, each of the above example components 300-312 andfeatures may be accessed, updated, or otherwise manipulated viadashboards and/or components through the application layer (e.g., via ahomepage) of a technical end-user platform, e.g., to provide homepagevisuals. Such information in provided in a unified, “one stop, onetool,” which provide a singular electronic location for planning andreporting. In such embodiments, data pulled, pushed, and/or queued fromvarious sources is integrated into singular view(s) as described herein.

FIG. 4 shows a representation of a plan selection GUI 400 of businessplanning software tool 202, consistent with the disclosed embodiments.For example, plan selection GUI 400 may be associated with goalcomponent 300, strategy component 302, or action plan component 304 andmay allow a user to initiate creation or modification of an agent'sbusiness plan.

As shown, plan selection GUI 400 may include agent information 402identifying: (1) the agent 108, such as by name and/or agent ID (e.g.,Charles Totoro), for whom a business plan is being created or modified;(2) the territory in which the agent 108 operates; (3) the date sincewhich the agent 108 has been an insurance agent on behalf of theinsurance provider; and (4) an identification of the contract underwhich the agent 108 works with the insurance provider. Plan selectionGUI 400 may include a year interface element 404 allowing the agent 108or other team member on behalf of the agent 108 to select a year forwhich to create a new business plan or modify an existing business plan.Plan selection GUI 400 may also include a continue interface element406, the selection of which causes business planning software tool 202to initiate creation of a new business plan or modification of anexisting business plan.

For example, selection of continue interface element 406 may causebusiness planning software tool 202 to proceed to business planobjective GUI 500, shown in FIG. 5 . Business plan objective GUI 500 mayallow the agent 108 or other team member to select which goal objectivesare deemed important in creating or modifying the business plan for theselected year. For example, business plan objective GUI 500 may includea grow or maintain my policy count interface element 502. The user mayselect grow or maintain my policy count interface element 502 if theagent has a goal to grow the number of active insurance policies sold bythat agent in one or more lines of business (e.g., auto and/or fire) forthe calendar year associated with the business plan.

Business plan objective GUI 500 may also have an increasing compensationinterface element 504. Insurance agents are often compensated by theinsurance providers on whose behalf they work periodically based on thenumber and type of policies in an active status, sold, or othercriteria. The user may provide input to select increasing compensationinterface element 504 if it is the agent's goal is to increase theagents compensation over the course of the calendar year associated withthe business plan, for example, by hitting certain growth targets orobjectives needed to qualify for increased compensation.

Business plan objective GUI 500 may include an agent incentive programinterface element 506. The agent or other team member may provide inputto select agent incentive program interface element 506 if it is a goalto increase the agents' qualifications for incentive programs offered bythe insurance provider over the course of the calendar year associatedwith the business plan. For example, by selling a certain number ofpolicies, or a certain number of policies of a qualifying type, theagent may qualify for a certain incentive program. Examples include anall-expenses paid vacation, promotional deals, free goods or services,etc.

Business plan objective GUI 500 may further include a small businesspremier program interface element 508. The user may provide input toselect small business premier program interface element 508 if the agenthas a goal to sell enough qualifying insurance policies in order toqualify for the Small Business Premier Program. For example, if an agent108 sells enough policies of a certain type, the agent may qualify for aprogram that recognizes or highlights prominent insurance professionalsor companies working in certain lines of business, having a particularinterest or focus in a line of business, having received awards fortheir performance, etc.

Business plan objective GUI 500 may have a back interface element 510,the selection of which causes business planning software tool 202 toreturn to plan selection GUI 400 (FIG. 4 ). Business plan objective GUI500 may also have a next interface element 512, the selection of whichcauses business planning software tool 202 to proceed to setting goalsGUIs, discuss below.

FIG. 6 shows an example of business plan objective GUI 500 afterselection of grow or maintain my policy count interface element 502. Forexample, GUI 500 may present grow or maintain auto, fire, life, and/orhealth insurance policy count interface elements 600-606 as drop-downinterface elements. If the agent has a goal to grow or maintain theagent's number of active auto, fire, life, and/or health insurancepolicies for the calendar year associated with the business plan, theuser may select respective elements 600-606. Each of elements 600-608may be associated with a corresponding number of policies to grow byinterface element 610. The user may use grow by interface elements 610to enter the number of polices by which the agent has a goal to grow theauto, fire life, or health insurance lines of business, respectively, inthe calendar year for the business plan.

FIG. 7 shows an example of business plan objective GUI 500 afterselection of increasing compensation interface component 504. Forexample, business plan objective GUI 500 may present compensation policyinterface elements 700-704 for auto, fire, and life insurance lines ofbusiness, respectively. Each of compensation policy interface elements700-704 may be associated with a corresponding compensation percentagegrowth interface element 706 (e.g., a slider) and compensation policynumber growth interface element 708. If the agent has a goal to grow theagent's compensation for the auto line of business by 3% in the calendaryear for the business plan, for example, the user may adjust thecompensation percentage growth interface element 706 for auto to 3%.Alternatively, if the agent has a goal to grow the agent's compensationfor the auto line of business based on a certain number of policies, theuser may input that number into the compensation policy number growthinterface element 708 for auto, and business planning software tool 202may compute the corresponding percentage and display it within interfaceelement 708 as shown in FIG. 7 . The compensation percentage growthinterface elements 706 and policy number growth interface elements 708for the fire and life insurance lines of business may operate in thesame way as described for the auto line of business.

FIG. 8 shows an example of business plan objective GUI 500 afterselection of incentive program interface element 606. For example,business plan objective GUI 500 may present incentive selectioninterface element 800, which may be a drop-down menu. Incentive programselection interface element 800 may list as options a plurality ofavailable incentive programs 802 (e.g., Honor Club, Ambassador TravelClub, etc.) The user may provide input to incentive program selectioninterface element 800 to select a desired incentive program 802 forwhich the agent has a goal to qualify in the calendar year of thebusiness plan. The user may use next interface element 804 to addanother incentive program selection interface element 806 to select anadditional incentive program for which the agent has a goal to qualifyin the calendar year of the business plan.

FIG. 9 shows an example of business plan objective GUI 500 afterselection of small business premier program interface element 608. Forexample, business plan objective GUI 500 may present small businesspremier program qualification requirements 900, which may indicate thenumber of qualifying policies in each line of business—such as auto andfire insurance policies—the agent must sell in the calendar year for thebusiness plan to qualify for the Small Business Premier Program.

Once the user has finished using business plan objective GUI 500 toselect the desired objectives for the business plan, the agent mayprovide input to next interface element 512. Next interface element 512may cause business planning software tool 202 to determine which of aplurality of goal setting GUIs, discussed below, to display, allowingthe agent to continue creating the business plan.

FIG. 10 shows an exemplary auto insurance goal setting GUI 1000,consistent with the disclosed embodiments. Business planning softwaretool 202 may be configured to display auto insurance goal setting GUI1000 when it is determined that the agent has used business planobjective GUI 500 to select grow or maintain my policy count interfaceelement 502 and to further select grow or maintain auto insurance policycount interface element 600. As explained below, auto insurance goalsetting GUI 1000 may conveniently provide information the user needs toquickly and efficiently generate a portion of the agent's business planfor the auto insurance line of business. Auto insurance goal setting GUI1000 provides a visual representation of the agent's historical,present, and planned future performance with respect to policies havingcertain statuses in each year. This gives the agent a feel for how theagent is currently performing relative to the agent's past performanceand helps the agent set goals going forward for future performance.Additionally, auto insurance goal setting GUI 1000 may provide aconvenient interface through which the agent may customize andexperiment with different potential goals and see how those goals, ifmet, relate to the agent's past and present performance. This helps theagent continue contributing to the growth of the insurance provider'sbusiness in a systematic and sustainable way.

As shown, auto insurance goal setting GUI 1000 may include a policycount chart 1002 for the agent. Policy count chart 1002 may show anumber of auto insurance policies 1004 assigned to the agent (e.g., soldby, managed by, or otherwise belonging to the agent) having a certainstatus over a historical period of time through the present 1006. Policystatuses may include, for example, in force, new, reinstated,lapsed/canceled, transferred from another insurance company, raw new(e.g., an original, new policy), added (e.g., another policy added to anexisting customer's account), etc.

Policy count chart 1002 may also show a projected number of polices 1008to have the selected status during the future time period 1010 of thebusiness plan. Policy count chart 1002 may also show a historicaltrendline 1012 reflecting the number of auto insurance policies havingthe selected status over historical period of time through the present1006 and a projected trendline 1014 adjusted based on the number ofpolices projected to have the selected status during future time periodof the business plan 1010.

Auto insurance goal setting GUI 1000 may have a chart policy statusselection interface element 1016 allowing the agent to select theinsurance policy status reflected in policy count chart 1002. Forexample, policy status selection interface element 1016 may provideoptions for chart 1002 to reflect policies having an in-force, raw new,added, reinstated, transferred from another company, and/orlapsed/canceled status during historical period of time through thepresent 1006 and projected to have that status during future time periodof the business plan 1010. For example, the agent may use policy statusselection interface element 1016 to change the policy status reflectedby policy count chart 1002 from the in-force to the raw new policystatus. In response to this selection, policy count chart 1002 may beupdated to reflect, instead of the number of policies in force, thenumber of new polices belonging to the agent in historical time periodthrough present 1006 and the number of projected new policies belongingto the agent during future time period of the business plan 1010.

As shown in FIG. 10 , auto insurance goal setting GUI 1000 may furtherinclude a policy count table 1018 for the agent. In a historical trendsview 1019, policy count table 1018 may show a number of the agent's autoinsurance policies having a plurality of statuses 1020 during historicalperiod of time through the present 1006 and projected to have theplurality of statuses 1020 for future time period 1010 of the businessplan. It is to be appreciated that policy count table 1018 may containthe same or similar information to that of policy count chart 1002. Incontrast to policy count chart 1002 which may only show information forone policy status at a time—the policy status currently selected usingchart type selection interface element 1016—policy count table 1018 mayshow information for a plurality of policy statuses 1020 simultaneously,with each status reflected in a particular row. For example, as shown inFIG. 10 , policy count table 1018 may list the number of the agent's netgained policies (with a gain ratio); lapsed/canceled policies (with alapsed/canceled ratio); new policies broken down by added, reinstated,intercompany-transferred, and raw new policies; and/or policies in forceover historical period of time through the present 1006 and projected tohave those statuses during future time period 1010 of the business plan.

Business planning software tool 202 may be configured to automaticallypopulate policy count chart 1002 and policy count table 1018 based oninformation stored in insurance policy databases 102. For example, basedon agent information 402 entered in plan selection GUI 400 (FIG. 1 ),such as the agent's ID, business planning software tool 202 mayretrieve, over network 104, auto insurance policy information associatedwith the agent stored in auto insurance policy database 110 and may usethat information to populate policy count chart 1002 and policy counttable 1018. For instance, if the agent selects “policies in force” usingchart policy status selection interface element 1016, business planningsoftware 202 may determine from the retrieved information how manypolices the agent had in force in each period (e.g., year) overhistorical period of time through the present 1006 and populate policycount chart 1002 with bar graphs accordingly. Using known techniquesand/or mathematical models, business planning software tool 202 may alsocalculate and/or use projections to populate chart 1002 for historicalperiod of time through the present 1006, to the extent the year is notover, and for future time period 1010 of the business plan. Businessplanning software tool 202 may similarly generate and populate chart1002 for other policy statuses selected using chart policy statusselection interface element 1016.

Business planning software tool 202 may likewise populate policy counttable 1018 based on the information retrieved from auto insurance policydatabase 110. Specifically, business planning software tool 202 may usethe retrieved information to populate table 1018 with the total numberof policies of each policy status 1020 occurring in historical period oftime through the present 1006 and projected to occur in future timeperiod 1010 of the business plan. For example, to populate table 1018for the “raw new” policy status among the plurality of policy statuses1020, business planning software tool 202 may analyze the retrievedinsurance policy information to identify which of the agent's autoinsurance policies original, new policies occurred over historicalperiod of time through the present 1006 and calculate the total for eachyear. To the extent the year is not over, business planning software 202may calculate and/or use projections to populate table 1018 forhistorical period of time through the present 1006 and for future timeperiod 1010 of the business plan.

Also shown in FIG. 10 , policy count table 1018 may also include a goalinput interface 1022. Using goal input interface 1022, the agent mayinput respective goal numbers of policies of each policy status 1020 toachieve in future time period 1010 of the business plan. For example, asshown in FIG. 10 , the agent is projected to net 489 new auto insurancepolicies in 2020 and, using goal input interface 1022, has input a goalof netting 400 new auto insurance policies for future time period 1010of the business plan (i.e., 2021). As another example, policy counttable 1018 shows that the agent is projected to have 3,193 policies inforce through the end of 2020 and, using goal input interface 1022, hasset a goal to have 3,293 policies in force 2021 (i.e., future timeperiod 1010 of the business plan).

Business planning software tool 202 may be configured to update policycount chart 1002 based on input to goal input interface 1022.Specifically, based on the goal numbers input to goal input interface1022, business planning software tool 202 may repopulate or regeneratethe portion of policy count chart 1002 corresponding to future timeperiod 1010 of the business plan. For instance, in the example of FIG.10 in which chart 1002 is a bar graph and chart policy status selectioninterface element 1016 is set to the status “policies in force,”business planning software tool 202 may increase or decrease the heightof the bar corresponding to future time period 1010 when the agentincreases or decreases the number input into goal input interface 1022corresponding to the “policies in force” policy status 1020.Additionally, business planning software tool 202 may appropriatelyadjust historical and projected trendlines 1012, 1014 based on the inputto goal input interface 1022.

As shown in FIG. 10 , auto insurance goal setting GUI 1000 may furtherinclude a reset goals interface element 1024. When interface element1024 receives input, business planning software tool 202 may reset thevalues in goal input interface 1022 to default values. For example,business planning software tool 202 may calculate default goal numbersof policies for each policy status 1020 for future time period 1010 andpopulate goal input interface 1022 with the default values. The defaultgoal values may be calculated in any appropriate way, such as byincreasing the values for the most recent year of historical period oftime through the present 1006 by a certain percentage (e.g., 5%, theaverage yearly increase over time period 1006, etc.). Business planningsoftware tool 202 may similarly populate goal input interface 1022 withdefault values when initially displaying auto insurance goal setting GUI1000, allowing the agent to change the default values if the agent haspolicy goals that differ from the default values.

As shown in FIG. 10 , auto insurance goal setting GUI 1000 may furtherinclude a next interface element 1026. When the agent has finished usingauto insurance goal setting GUI 1000 to complete the portion of theagent's business plan for the auto insurance line of business, the agentmay provide input to next interface element 1026. This may causebusiness planning software tool 202 to save the agent's business plan indatabase 116. Next interface element 1026 may additionally causebusiness planning software tool 202 to proceed to the goal setting GUIfor the next objective (e.g., additional lines of business, increasingcompensation, agent incentive programs, small business premier program)the agent identified as an objective using interface elements 502-508.

FIG. 11 shows auto insurance goal setting GUI 1000 upon selection of acurrent year view 1028 for policy count table 1018. As shown, currentyear view 1028 may include goal input interface 1022 from FIG. 10 butmay further include a second goal input interface 1100. Whereas goalinput interface 1022 may allow the agent to enter goal numbers ofpolicies of each policy status 1020 to achieve in future time period1010 of the business plan as numeric values, second goal input interface1100 may include sliders or other interface elements (e.g., dials)allowing the agent to set the goal numbers across a continuous range.When a goal number is entered into goal input interface 1022, businessplanning software tool 202 may adjust second goal input interface 1100accordingly, and vice versa. For example, if the agent enters a goal of400 policies for the lapsed/canceled policy status 1020 into goal inputinterface 1022, business planning software tool 202 may adjust thecorresponding slider (or other interface element) of second goal inputinterface 1100 for the lapsed/canceled policy status 1020 to a positionwithin the range corresponding to 400. And, likewise, if the agentadjusts the slider or other interface element of second goal inputinterface 1100 to a position within the range corresponding to 180 “new”added policies, as shown, business planning software tool 202 maypopulate goal input interface 1022 for the “new” policy status 1020 withthe number 180.

FIGS. 12 and 13 respectively show exemplary fire insurance and lifeinsurance goal setting GUIs 1200, 1300, consistent with the disclosedembodiments. Business planning software tool 202 may be configured todisplay fire insurance goal setting GUI 1200 when it is determined thatthe agent has used business plan objective GUI 500 to select grow ormaintain my policy count interface element 502 and to further selectgrow or maintain my fire policy count interface element 602. Likewise,business planning software tool 202 may be configured to display lifeinsurance goal setting GUI 1300 when it is determined that the agent hasselected grow or maintain my policy count interface element 502 andfurther selected grow or maintain my life policy count interface element604.

Similar to auto insurance goal setting GUI 1000, fire and life insurancegoal setting GUIs 1200, 1300 may conveniently provide information theagent needs to quickly and efficiently generate portions of a businessplan for the fire and life insurance lines of business, respectively.Goal setting GUIs 1200 and 1300 give the agent a visual representationof the agent's historical, present, and planned future performance withrespect to various policy statuses (e.g., new, lapsed/canceled,in-force, reinstated, etc.) in each year. This gives the agent a feelfor how the agent is currently performing relative to the agent's pastperformance across policy statuses and helps the agent set goals goingforward for future performance in the fire and life insurance lines ofbusiness. Additionally, goal setting GUIs 1200, 1300 may provideconvenient interfaces through which the agent may customize andexperiment with different potential goals and see how those goals, ifmet, compare to the agent's past and present performance. Whereas thedifficult and haphazard nature of conventional business planning in theinsurance industry discourages agents from creating and adhering tobusiness plans, the ease with which the agent may generate the fire andlife insurance portions of the business plan using goal setting GUIs1200, 1300 encourages agents to regularly create and use business plansin their day-to-day work. Thus, agents may continue contributing to thegrowth of their own business, as well as the insurance provider'sbusiness generally, in a systematic and convenient way.

Fire insurance and life insurance goal setting GUIs 1200, 1300 may havea similar configuration and operation to auto insurance goal setting GUI1000 discussed above but may have information relating to the agent'sfire and life insurance policies, respectively, rather than to theagent's auto insurance policies. For example, as shown in FIGS. 12 and13 , goal setting GUIs 1200 and 1300 may have respective policy countcharts 1002 for the fire and life insurance lines of business showingthe agent's performance with respect to policies having a certain statusselected using chart policy status selection interface element 1016 overhistorical period of time through the present 1006 and projected forfuture time period 1010 of the business plan.

Likewise, goal setting GUIs 1200 and 1300 may similarly have respectivepolicy count tables 1018 for the fire and life insurance lines ofbusiness with a historical view showing the number of auto insurancepolicies of a plurality of statuses 1020 belonging to the agent overhistorical period of time through the present 1006 and projected forfuture time period 1010 of the business plan. As with the auto insuranceline of business, policy count tables 1018 for the fire and lifeinsurance lines of business may include respective goal input interfaces1022, 1100 allowing input of respective goal numbers of policies of eachpolicy status 1020 to achieve in future time period 1010 of the businessplan. Additionally, goal setting GUIs 1200, 1300 may include nextinterface elements 1026 allowing the agent to respectively save the fireand life insurance portions of the agent's business plan in database 116and cause business planning software tool 202 to proceed to the goalsetting GUI for another objective (e.g., additional lines of business,increasing compensation, agent incentive programs, small businesspremier program) the agent identified as an objective using interfaceelements 502-508 (FIG. 5 ).

FIG. 14 shows basic, high-level components of a computing device 1400through which agents 108 may access and use access insurance businessplanning system 106, including software tools 118. For example,computing device 1400 may be a desktop computer, a laptop computer, amobile device, or any other computing device known in the art. Computingdevice 1400 may communicate with insurance business planning system 106over network 104, including one or more local networks and/or theInternet.

Computing device 1400 may include processor(s) 1401 and memory 1402.Depending on exact configuration and type of computing device, memory1402 may be volatile (such as RAM), non-volatile (such as ROM, flashmemory, etc.) or some combination of the two. In some examples,processor(s) 1401 may be a central processing unit (CPU) or otherprocessing unit or component known in the art. Furthermore, theprocessor(s) 1401 may include any number of processors and/or processingcores. Processor(s) 1401 may be configured to retrieve and executeinstructions from the memory 1402, including instructions to perform theprocesses, methods, and steps described herein. Processor(s) 1401,executing the instructions, may perform the functions herein in concertwith insurance business planning system 106.

The memory 1402 may be described as non-transitory computer-readablemedia or machine-readable storage memory and may include removable andnon-removable media implemented in any method or technology for storageof information, such as computer executable instructions, datastructures, program modules, or other data. Memory 1402 may include, butis not limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile discs (DVD) or other opticalstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or any other tangible, physical mediumwhich can be used to store the desired information.

Computing device 1400 may include additional data storage devices(removable and/or non-removable) such as, for example, magnetic disks,optical disks, or tape. Such additional storage is illustrated in FIG.14 by removable storage 1404 and non-removable storage 1406. Tangiblecomputer-readable media can include volatile and non-volatile, removableand non-removable media implemented in any method or technology forstorage of information, such as computer readable instructions, datastructures, program modules, or other data for performing the functionsdisclosed herein. Memory 1402, removable storage 1404, and non-removablestorage 1406 are all examples of computer-readable storage media.Computer-readable storage media include, but are not limited to, RAM,ROM, EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile discs (DVD), content-addressable memory (CAM), or otheroptical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other medium which canbe used to store information. Any such tangible computer-readable mediacan be part of computing device 1400.

Memory 1402, removable storage 1404, and/or non-removable storage 1406may in some cases include storage media used to transfer or distributeinstructions, applications, and/or data. In some cases, memory 1402,removable storage 1404, and/or the non-removable storage 1406 mayinclude data storage that is accessed remotely, such as databases 102,116 that computing device 1400 access over network 104. In variousexamples, any or all of memory 1402, removable storage 1404, and/ornon-removable storage 1406 may store programming instructions that, whenexecuted, implement some or all of the function functionality describedherein.

Computing device 1400 may also include input device(s) 1408, such as akeypad, a cursor control, a touch-sensitive display, voice input device,etc., and output device(s) 1412 such as a display, speakers, printers,etc. These devices are well known in the art and need not be discussedat length here. And, as illustrated in FIG. 14 , computing device 1400may also include one or more wired or wireless transceiver(s) 1410. Forexample, 1 transceiver(s) 410 can include a network interface card(NIC), a network adapter, a LAN adapter, or a physical, virtual, orlogical address to connect to various networks, devices, or componentsillustrated in figures herein. To increase throughput when exchangingwireless data, transceiver(s) 1410 can utilizemultiple-input/multiple-output (MIMO) technology. Transceiver(s) 1410can comprise any sort of wireless transceivers capable of engaging inwireless, radio frequency (RF) communication. Transceiver(s) 1410 canalso include other wireless modems, such as a modem for engaging inWi-Fi, WiMAX, Bluetooth, infrared communication, and the like.

FIG. 15 shows an exemplary method 1500 for creating a business plan,consistent with the disclosed embodiments. Method 1500 may be performedby computing device 1400, in concert with insurance business planningsystem 106, executing business planning software tool 202 and/or othersoftware tools 118. For example, through business planning software tool202 and/or other software tools 118, computing device 1400 may interactwith insurance business planning system 106 over network 104 in aclient-server or client-cloud relationship to carry out method 1500.

In step 1502, a business plan may be initiated. For example, an agent108 or other team member (hereafter “user”) using computing device 1400may access business planning software tool 202. For example, the usermay log in to business planning software tool 202, and computing device1400 may present plan selection GUI 400 (FIG. 4 ). Using year interfaceelement 404, the agent may select the year for which the user desires tocreate or modify a business plan (e.g., 2021 or 2022).

In step 1504, the user may select objectives for the business plan. Forexample, the user may provide input to continue interface element 406,causing business planning software tool 202 to initiate creation and/ormodification of the business plan by proceeding to business planobjective GUI 500 (FIG. 5 ). Using business plan objective GUI 500, theuser may select objectives deemed important for the business plan duringthe plan year selected in step 1502. For example, desired objectives mayinclude growing the agent's policy count in the auto, fire, and lifeinsurance lines of business. Accordingly, the user may provide input toselect grow or maintain my policy count interface element 502, and thenfurther select interface elements 600-604 (FIG. 6 ). As another example,the user may only have the objective to grow the agent's policy count inthe auto insurance line of business and may therefore only select growor maintain auto insurance policy count interface element 600.

In step 1506, business planning software tool 202 may determine whetherthe user selected the objective to grow or maintain the agent's autoinsurance policy count in step 1504. If so, in step 1508, businessplanning software tool 202 may retrieve from auto insurance policydatabase 110, over network 104, auto insurance policy informationassociated with the agent. For example, business planning software tool202 may look up auto insurance policies associated with agentinformation 402 (e.g., the agent's name, agent ID, employee number,etc.), download the associated insurance policy information over network104, and store it in memory.

In step 1510, business planning software tool 202 may display autoinsurance goal setting GUI 1000 (FIG. 10 ) and populate it based on theauto insurance information associated with the agent retrieved in step1506. For example, business planning software tool 202 may populatepolicy count chart 1002 for a default policy status (e.g., policies inforce), as discussed above. Additionally, business planning softwaretool 202 may populate policy count table 1018 based on the autoinsurance information associated with the agent retrieved in step 1506,as discussed above.

In step 1512, the user may enter the agent's goals for the autoinsurance business objective into auto insurance goal setting GUI 1000.For example, as discussed above, the user may view the populated policycount chart 1002 and policy count table 1018 and assess the agent'sperformance in the auto insurance line of business over historicalperiod of time through the present 1006 and determine appropriate policycount goals for each policy status 1020 of policy for future time period1010 of the business plan (i.e., 2021). Having determined appropriategoals, the user may enter them into auto insurance goal setting GUI 1000using goal input interface 1022 and/or second goal input interface 1100(FIG. 11 ), as described above. Once the user is satisfied with theentered goals for the auto insurance line of business, the user mayprovide input to next interface element 1026, which may cause businessplanning software tool 202 to save the information entered into autoinsurance goal setting GUI 1000 for the auto insurance portion of thebusiness plan in memory and/or in business plan database 116.

Business planning software tool 202 may proceed to step 1514 followingstep 1512 and/or following step 1506 if it is determined that user didnot select the objective to grow or maintain the agent's auto insurancepolicy count. In step 1514, business planning software tool 202 maydetermine whether the user selected the objective to grow or maintainthe agent's fire insurance policy count in step 1504. If so, in step1516, business planning software tool 202 may retrieve from fireinsurance policy database 112, over network 104, fire insurance policyinformation associated with the agent. For example, business planningsoftware tool 202 may look up fire insurance policies associated withagent information 402 (e.g., the agent's name, agent ID, employeenumber, etc.), download the associated insurance policy information overnetwork 104, and store it in memory.

In step 1518, business planning software tool 202 may display fireinsurance goal setting GUI 1200 (FIG. 12 ) and populate it based on thefire insurance information associated with the agent retrieved in step1516. For example, business planning software tool 202 may populatepolicy count chart 1002 for a default policy status (e.g., policies inforce) for the fire insurance line of business, as discussed above.Additionally, business planning software tool 202 may populate policycount table 1018 based on the fire insurance information associated withthe agent retrieved in step 1506, as discussed above.

In step 1520, the user may enter the agent's goals for the fireinsurance business objective into fire insurance goal setting GUI 1200.For example, as discussed above, the user may view the populated policycount chart 1002 and policy count table 1018 and assess the agent'sperformance in the fire insurance line of business over historicalperiod of time through the present 1006 and determine appropriate policycount goals for each policy status 1020 for future time period 1010 ofthe business plan (e.g., 2021). Having determined appropriate goals forthe agent's fire insurance line of business, the user may enter theminto GUI 1200 using goal input interface 1022 and/or second goal inputinterface 1100, as described above. Once the user is satisfied with theentered goals for the fire insurance line of business, the user mayprovide input to next interface element 1026, which may cause businessplanning software tool 202 to save the information entered into goalsetting GUI 1200 for the fire insurance portion of the business plan inmemory and/or in business plan database 116.

Business planning software tool 202 may proceed to step 1522 followingstep 1520 and/or following step 1514 if it is determined that user didnot select the objective to grow or maintain the agent's fire autoinsurance policy count. In step 1522, business planning software tool202 may determine whether the user selected the objective to grow ormaintain the agent's life insurance policy count in step 1504. If so, instep 1524, business planning software tool 202 may retrieve from lifeinsurance policy database 114, over network 104, fire insurance policyinformation associated with the agent. For example, business planningsoftware tool 202 may look up life insurance policies associated withagent information 402 (e.g., the agent's name, agent ID, employeenumber, etc.), download the associated insurance policy information overnetwork 104, and store it in memory.

In step 1526, business planning software tool 202 may display lifeinsurance goal setting GUI 1300 (FIG. 13 ) and populate it based on thelife insurance information associated with the agent retrieved in step1524. For example, business planning software tool 202 may populatepolicy count chart 1002 for a default policy status (e.g., policies inforce) for the life insurance line of business, as discussed above.Additionally, business planning software tool 202 may populate policycount table 1018 based on the life insurance information associated withthe agent retrieved in step 1506, as discussed above.

In step 1528, the user may enter the agent's goals for the lifeinsurance business objective into fire insurance goal setting GUI 1300.For example, as discussed above, the user may view the populated policycount chart 1002 and policy count table 1018 and assess the agent'sperformance in the life insurance line of business over historicalperiod of time through the present 1006 and determine appropriate policycount goals for each policy status 1020 for future time period 1010 ofthe business plan (e.g., 2021). Having determined appropriate goals forthe agent's life insurance line of business, the user may enter theminto GUI 1300 using goal input interface 1022 and/or second goal inputinterface 1100, as described above. Once the user is satisfied with theentered goals for the life insurance line of business, the user mayprovide input to next interface element 1026, which may cause businessplanning software tool 202 to save the information entered into GUI 1300for the life insurance portion of the business plan in memory and/or inbusiness plan database 116.

In step 1530, insurance business planning software tool 202 may save theagent's business plan in business plan database 116. The user mayperiodically return to business planning software tool 202 at anydesired time to view the business plan, modify any aspects of thebusiness plan, and see the agent's progress towards hitting thepreviously set goals. For example, when the user accesses any of thegoal setting GUIs 1000, 1200, 1300 at a later date, business planningsoftware tool 202 may re-populate the GUIs with the most recentinsurance information from insurance provider databases 102 so that theagent's progress towards the goals can be seen. That is, businessplanning software tool 202 may update the information displayed inpolicy count chart 1002 and policy count table 1018 in the goal settingGUIs 1000, 1200, 1300 for each line of business.

Using this updated information, the user may check the agent's goals tosee if they remain appropriate or warrant any modifications. Forexample, the user may check that projected trendline 1014 remains ontrack with, or exceeding, historical trendline 1012. This may indicatethat the agent's recent and projected future performance remains on parwith the agent's historical performance, and the agent can expect futuregrowth in the near term consistent with the agent's historical growth ina particular line of business. If the agent's performance does notappear on track to achieve the goals, adjustments can be made inadvance. For example, perhaps the original goals were too ambitious, andso the user via goal setting GUIs 1000, 1200, 1300 may reduce the goalsto more realistic goals. Or, perhaps, the agent's performance leavesroom for improvement, and the agent can be notified so that the agentcan take early steps to increase performance, get on track, and achievethe original goals without modification.

Additionally, the updated policy count tables 1018 of goal setting GUIs1000, 1200, 1300 provide the user with a snapshot of how the agent isperforming, not just within the particular line of business, but withineach particular policy status 1020. This is helpful because an agent maybe overperforming, adequately performing, or underperforming withrespect to certain policy statuses 1020, and performance within eachpolicy status in the aggregate determines the agent's overallperformance and progress toward a goal. For example, at a given point intime, despite performing adequately on added and new policy statuses,the agent might be significantly underperforming on reinstated policystatuses, bringing the agent's overall performance on the new policystatus below the agent's goal. Armed with this information, the agentmay shift from a new customer drive to focus efforts on getting existingor former customers whose policies have recently lapsed or been canceledto reinstate their policies.

As shown in FIG. 15 , method 1500 may include taking next steps 1532with the completed business plan. It will be appreciated that, once abusiness plan is complete, it may be distributed to other team membersand partners to help enact and put the plan into action. For example,the completed business plan may be transmitted to or shared with othersoftware tools 118—such as digital whiteboard software tool 204, teammember incentives software tool 206, a reporting software tools208—which may further process the business plan and allow other teammembers and partners to view the business plan and take additional stepsto implement it.

Next steps 1532 may include creating a marketing plan based on thebusiness plan. For example, action plan component 304 may presenthistorical marketing data and historical leading indicator results foreach line of business. Using digital whiteboard software tool 204, teammembers may set activity goals at the insurance agent office level.Then, specific activity goals may be distributed to the team. Actionplan component 304 may display a summary of marketing data for each lineof business, aligned with the activity goals set by the team. Then thegoals may be shared with the agent's customers/business partners, overnetwork 104, via Electronic Customer Relationship Management (ECRM)systems.

Next steps 1532 may further include assigning the goals of the businessplan to the agent's team members using goal distribution component 306.For example, goal distribution component 306 may be used to identifyteam members who will be responsible for what activities and generate ateam plan. Goal distribution component 306 may be used to distributegoals and action items. In some embodiments, team members may beassigned their own, smaller team member plan as part of a lagerelectronic plan. Such detailed level of planning may result in sharedaccountability among the team. Various integration GUIs may provideaccess to the goal-distribution based feature, e.g., to visit theirdistributed/assigned goal. Additionally, goal distribution component 306may transmit the goals of the business plan to the customers/businesspartners via the ECRM.

Next steps 1532 may further include setting leading indicator (activity)goals. For example, using digital whiteboard software tool 204, activitygoals may be set at the office level. The activity goals may be assignedto team members and also sent to the ECRM.

While the invention is described with respect to the specific examples,it is to be understood that the scope of the invention is not limited tothese specific examples. Since other modifications and changes varied tofit particular operating requirements and environments will be apparentto those skilled in the art, the invention is not considered limited tothe example chosen for purposes of disclosure and covers all changes andmodifications which do not constitute departures from the true spiritand scope of this invention.

For example, business planning software tool 200 may have additionalgoal setting GUIs beyond the examples described for auto, fire, and lifeinsurance 1000, 1200, 1300. As an example, business planning softwaretool 202 may include goal setting GUIs for other types of financialservices or products besides life insurance, such as banking, wealthmanagement, mutual funds, etc. Goal setting GUIs for other types ofinsurances may also be included, such as motorcycle, boating, mobilehome, general liability, medical malpractice insurance, etc.

Although the application describes embodiments having specificstructural features and/or methodological acts, it is to be understoodthat the claims are not necessarily limited to the specific features oracts described. Rather, the specific features and acts are merelyillustrative some embodiments that fall within the scope of the claimsof the application.

What is claimed is:
 1. A computer-implemented method for generating aninsurance business plan, the method comprising: receiving anidentification of an agent associated with the insurance business planand a selection of a future time period for the insurance business plan;displaying a business plan objective graphical user interface (GUI)presenting for selection a plurality of insurance business planobjectives, wherein one of the objectives is to grow or maintaininsurance policy counts for one or more insurance lines of business;receiving, via the business plan objective GUI, a selection of theobjective to grow or maintain insurance policy counts for one or morelines of business; displaying for selection, based on a determinationthat the objective to grow or maintain insurance policy counts for oneor more lines of business has been selected, a plurality of insurancelines of business; receiving, via the business plan objective GUI, aselection of an insurance line of business of the plurality of insurancelines of business; retrieving, from an insurance policy database over anetwork, insurance policy information for insurance policies assigned tothe agent in the selected line of business; and displaying a goalsetting GUI for the selected line of business, the goal setting GUIbeing populated based on the retrieved insurance policy information andincluding a policy count chart showing a number of insurance policiesassigned to the agent having a selected status, among a plurality ofstatuses, during a historical period of time through the present andshowing a number of polices projected to have the selected status duringthe selected future time period of the business plan.
 2. The method ofclaim 1, wherein the plurality of insurance lines of business includesone or more of auto insurance, fire insurance, and life insurance. 3.The method of claim 1, wherein the plurality of statuses includes one ormore of in-force, raw new, added, reinstated, transferred from anotherinsurance company, and lapsed/canceled.
 4. The method of claim 1,wherein the goal setting GUI further includes a policy count tableshowing a number of insurance policies assigned to the agent having eachof the plurality of statuses during the historical period of timethrough the present and projected to have each of the plurality ofstatuses during the selected future period of time of the business plan.5. The method of claim 1, wherein the goal setting GUI further includesa goal input interface configured to receive input of respective goalnumbers of policies having each of the plurality of statuses for theselected future period of time of the business plan.
 6. The method ofclaim 5, further comprising storing, in a business plan database, thebusiness plan with the input goal numbers of policies having each of theplurality of statuses for the selected future time period of thebusiness plan.
 7. The method of claim 5, further comprising updating oneor more of the policy count chart and the policy count table based onthe input goal numbers of policies having each of the plurality ofstatuses for the selected future time period of the business plan.
 8. Acomputer-readable storage medium storing computer program instructionsthat, when executed by a processor, cause the processor to perform amethod of generating an insurance business plan, the method comprising:receiving an identification of an agent associated with the insurancebusiness plan and a selection of a future time period for the insurancebusiness plan; displaying a business plan objective graphical userinterface (GUI) presenting for selection a plurality of insurancebusiness plan objectives, wherein one of the objectives is to grow ormaintain insurance policy counts for one or more insurance lines ofbusiness; receiving, via the business plan objective GUI, a selection ofthe objective to grow or maintain insurance policy counts for one ormore lines of business; displaying for selection, based on adetermination that the objective to grow or maintain insurance policycounts for one or more lines of business has been selected, a pluralityof insurance lines of business; receiving, via the business planobjective GUI, a selection of an insurance line of business of theplurality of insurance lines of business; retrieving, from an insurancepolicy database over a network, insurance policy information forinsurance policies assigned to the agent in the selected line ofbusiness; and displaying a goal setting GUI for the selected line ofbusiness, the goal setting GUI being populated based on the retrievedinsurance policy information and including a policy count chart showinga number of insurance policies assigned to the agent having a selectedstatus, among a plurality of statuses, during a historical period oftime through the present and showing a number of polices projected tohave the selected status during the selected future time period of thebusiness plan.
 9. The computer-readable storage medium of claim 8,wherein the plurality of insurance lines of business includes one ormore of auto insurance, fire insurance, and life insurance.
 10. Thecomputer-readable storage medium of claim 8, wherein the plurality ofstatuses includes one or more of in-force, raw new, added, reinstated,transferred from another insurance company, and lapsed/canceled.
 11. Thecomputer-readable storage medium of claim 8, wherein the goal settingGUI further includes a policy count table showing a number of insurancepolicies assigned to the agent having each of the plurality of statusesduring the historical period of time through the present and projectedto have each of the plurality of statuses during the selected futureperiod of time of the business plan.
 12. The computer-readable storagemedium of claim 8, wherein the goal setting GUI further includes a goalinput interface configured to receive input of respective goal numbersof policies having each of the plurality of statuses for the selectedfuture period of time of the business plan.
 13. The computer-readablestorage medium of claim 12, wherein the method further includes storing,in a business plan database, the business plan with the input goalnumbers of policies having each of the plurality of statuses for theselected future time period of the business plan.
 14. Thecomputer-readable storage medium of claim 12, wherein the method furtherincludes updating one or more of the policy count chart and the policycount table based on the input goal numbers of policies having each ofthe plurality of statuses for the selected future time period of thebusiness plan.
 15. A computing terminal, comprising; a memory storingcomputer program instructions; and one or more processors configured toexecute the instructions to perform a method for generating an insurancebusiness plan, including to: receive input of an identification of anagent associated with the insurance business plan and a selection of afuture time period for the insurance business plan; display a businessplan objective graphical user interface (GUI) presenting for selection aplurality of insurance business plan objectives, wherein one of theobjectives is to grow or maintain insurance policy counts for one ormore insurance lines of business; receive, via the business planobjective GUI, a selection of the objective to grow or maintaininsurance policy counts for one or more lines of business; display forselection, based on a determination that the objective to grow ormaintain insurance policy counts for one or more lines of business hasbeen selected, a plurality of insurance lines of business; receive, viathe business plan objective GUI, a selection of an insurance line ofbusiness of the plurality of insurance lines of business; cause theretrieval, from an insurance policy database over a network, insurancepolicy information for insurance policies assigned to the agent in theselected line of business; and display a goal setting GUI for theselected line of business, the goal setting GUI being populated based onthe retrieved insurance policy information and including a policy counttable showing a number of insurance policies assigned to the agenthaving each of a plurality of statuses during the historical period oftime through the present and projected to have each of the plurality ofstatuses during the selected future period of time of the business plan.16. The computing terminal of claim 15, wherein the plurality ofinsurance lines of business includes one or more of auto insurance, fireinsurance, and life insurance.
 17. The computing terminal of claim 15,wherein the plurality of statuses includes one or more of in-force, rawnew, added, reinstated, transferred from another insurance company, andlapsed/canceled.
 18. The computing terminal of claim 15, wherein thegoal setting GUI further includes a policy count chart showing a numberof insurance policies assigned to the agent having a selected status,among the plurality of statuses, during the historical period of timethrough the present and showing a number of polices projected to havethe selected status during the selected future time period of thebusiness plan.
 19. The computing terminal of claim 15, wherein the goalsetting GUI further includes a goal input interface configured toreceive input of respective goal numbers of policies having each of theplurality of statuses for the selected future period of time of thebusiness plan.
 20. The computing terminal of claim 19, wherein the oneor more processors are further configured to execute the instructions tostore, in a business plan database, the business plan with the inputgoal numbers of policies having each of the plurality of statuses forthe selected future time period of the business plan.